With the generic order import, customers can transmit their order in an XML, which is read into the ingenious database via script and created as an order.

The settings for the document import are saved in the customer's contact record.

The file storage and the XML structure can be defined individually for each customer.

Configuration of the document XML import for a contact

Functions

The following functions are available via the icon bar for the settings of the XML document import:

	Inserts an article with its preconfiguration into the XML structure.
	Adds a new node.
	Deletes the selected node. (Nodes that are the minimum required for the structure cannot be removed.)
	Exports the XML template for forwarding to the customer. The Windows save dialog opens, in which the storage location can be selected and the filter name can be assigned.

File storage

FTP-Server

XML settings

The structure of the XML file is specified in the XML settings.

For each new customer configuration, the basic structure is loaded, which consists of the header and the item list.

For each node name, the link to the database field or partlist variable an optional individual description, a possible default value and the identifier for a mandatory field are given.

Structure of the header

The header data of the order document are specified in the header.

Standard node

The standard nodes represent the minimum configuration of the XML structure.

These must be included in the XML supplied by the customer.

Standard nodes cannot be deleted.

Additional nodes

Additional nodes can be added to the header using the button .

With the node <DELIVERY_DATE> with the link a the project field, e.g. date_9, the customer can submit a requested delivery date, for example.

Structure of the item list

All items of an order are listed in the item list <ITEM_LIST>.

A node <ITEM> is written for each position, which contains the following standard elements:

For each article to be ordered, all properties must be defined with which it can clearly identified or produced.

For products that are manufactured from several individual parts, in formation about the desired design must also be provided.

All variants of a complex product are defined in the so-called partlists.

For each property a variable is defined which can contain different values.

All the necessary variables for such an article must be listed in the XML structure.

Partlist configuration

The desired part list can be loaded via the item search using the button .

The checklist opens in which it is determined which options should be included in the XML (1st checkbox) and which option must be filled in (2nd checkbox).

In addition a standard configuration can already be set.

If no values are entered for individual options in the XML transmitted by the customer, the standard value is accepted (e.g. the customer always orders a certain profile type or color).

Configuration of a partlist for the XML order import of a customer

All parameters of a partlist are loaded into the XML structure according to the previous configuration.

The details of the individual nodes can then be edited further.

For example, the possible values of a parameter can be specified in the description for information for the customer.

Item node of a partlist

A part list can also be preconfigured in the article data and is then available for all customer configurations when the article is added.

see Sourcecode View and Measurement

Transfer of the XML

Once the XML structure has been defined, a template for the customer can be exported using the button  .

With the help of this template the customer can (let) program an export of his order for his software.

<?xml version="1.0" encoding="UTF-8"?>
 <DOCUMENT mandatory="true">
  <HEADER mandatory="true">
   <CUSTOMER mandatory="true" description="Short name of the customer">Doe, John</CUSTOMER>
   <NAME mandatory="true" description="Name of the document">Order confirmation</NAME>
   <NUMBER mandatory="true" description="Project or own purchase order number"/>
   <DELIVERY_DATE description="Desired delivery date"/>
  </HEADER>
  <ITEM_LIST mandatory="true">
   <ITEM>
    <ITEM-ID mandatory="true"/>
    <ITEM-NAME mandatory="true"/>
    <QUANTITY mandatory="true">1</QUANTITY>
    <X>100</X>
    <Y>100</Y>
    <Z>100</Z>
   </ITEM>
   <ITEM>
    <ITEM-ID mandatory="true">RS</ITEM-ID>
    <ITEM-NAME mandatory="true">Rolling Shutter</ITEM-NAME>
    <QUANTITY mandatory="true">1</QUANTITY>
    <X mandatory="true">100</X>
    <Y mandatory="true">100</Y>
    <vKType>45°</vKType>
    <vKSize>137</vKSize>
    <vKColor>white</vKColor>
    <vPType mandatory="true">ALU</vPType>
    <vPSize mandatory="true">32</vPSize>
    <vPColor mandatory="true" description="Color: PVC: white, beige, brown, dark green, grey ALU: white, beige, brown, grey, RAL">white</vPColor>
    <vEType>False</vEType>
    <vEDiffColor>False</vEDiffColor>
    <vEColor>white</vEColor>
    <vStopType>False</vStopType>
    <vFSType>ALU</vFSType>
    <vFSSize>Mini</vFSSize>
    <vFSDiffColor>False</vFSDiffColor>
    <vFSColor>white</vFSColor>
    <vFSLonger>0</vFSLonger>
    <vFSBevel>0</vFSBevel>
    <vFSCover>False</vFSCover>
    <vControlSide>left</vControlSide>
    <vControlType>Tape coiler</vControlType>
    <vControlColor>white</vControlColor>
</ITEM>
</ITEM_LIST>
</DOCUMENT>

Import of the order data

The import of the order data itself is executed time-controlled by the scheduler.

To do this, a script is to be created with the following call:

public void XML_Import(out bool bError, out string sResult, out string sDescription)
{
    bError = false;
    sResult = "";
    sDescription = "";
    ingenious.net.Moduls.ProjectXmlImport.Import.Start(out bError, out sResult, out sDescription);
}

In the scheduler this script is then selected in the general task planning as the method to be executed.